Nice improvement, but I can see some regression issues in the UI. The Title column in the Guidance section is not rendered correctly.

PR:

Master:

I think the use of "Enter" is a pattern across Phoebus where any text input for the user is applied after and explicit "Enter"
This makes a lot of sense when you think about it from a control system point of view... you have started typing out a value to write to the PV and you accidentally or inadvertently click the mouse causing a change in focus... you do not want the incorrect/incomplete value to be written to the control system.

Coming to this PR.
I guess there is merit in not applying this rigid text input/editing rule to places like the alarm configuration, log entry dialog, save and restore desc/comment, etc...even if it means inconsistent text input behaviors across apps ( and at times within the same app )

@kasemir what are your thoughts?

We do want confirmation (via ENTER) in text entry fields and similar at runtime. In there, when you leave the text field (move out of focus), staying at the previous PV value is the safe thing to do. In comparison, running a motor to a half-typed position because somebody accidentally moved the mouse might shear somebody's arm off.

In the editor, we already accept text when leaving the field for PV names or a Label text. So I'm OK with generally accepting text in the editor. Amazon accepts my credit card number when I leave the text field, so that's industry standard. Still, for the display runtime, we need confirmation.

In this case when you press the enter key, the new configuration is not sent to kafka until you press the OK button of the dialog box. In my opinion, there is no risk to validate when you click somewhere else. as the ok button is the true validation.

However, a lot of users at CEA are "Windows" users and do not use so much the keyboard but the mouse. If you type a long text in the edit and then you forget (or don't know you have to) to validate with the Enter key, then you loose all your text which can be a bit annoying, particularly if you also forget the second time...

Nice improvement, but I can see some regression issues in the UI. The Title column in the Guidance section is not rendered correctly.

PR:

Master:

I cannot reproduce your problem.
On my computer i have this :

Do you have the problem with only the Guidance ? It should happen to Displays, ... too
Can you tell the steps to reproduce it ?

I was not able to reproduce the error @georgweiss noticed
I tested on a windows machine